Component configuration
Components are the reusable configuration objects that are used in processes. They are displayed in the Component Explorer. Components can be created once and referenced by process steps across multiple processes.
| Components | Description |
|---|---|
| Process | Contains a series of steps that determine how data executes within the system. |
| API Proxy | Deployable components enables direct proxying of a request through an API Gateway to a service that is not served through a runtime, runtime cluster, or runtime cloud. |
| API Service | Deployable components used to expose sets of REST, SOAP, or OData API endpoints for logical groups of APIs. |
| Flow Service | Provides a means by which a service interacts with processes. It is independently deployable, enabling a single component to support all requests specifying a common endpoint. |
| Certificate | Ensures secure data transmission across the communication protocol. Certain connectors require certificates to encrypt data and channels and to verify the digital signature of the person sending the data. |
| Connection | Contains the configuration required to connect to an application or data source. |
| Connector Operation | Represents a specific action or API call against the application or data source defined by the connection. |
| Cross Reference Table | The cross reference table is a data structure that replaces a run time lookup computation with a much simpler lookup operation. |
| Custom Library | Collections of Java Archive (JAR) files that you can use to support certain integration processes. |
| Document Cache | Lets you temporarily hold and index Boomi documents within the scope of an integration process. |
| Map | Converts data from one layout or format to another. |
| Map Function | Enables the application of transformation logic to each individual field value during the mapping process. |
| Organization | Stores contact information in a reusable component. |
| Process Property | Consists of a collection of properties. |
| Process Route | Lets you select an execution path dynamically at run time based on some value, such as a document property, data profile, extension value, or trading partner. |
| Profile | Describes the layout or format of documents read into or sent out of processes. |
| Queue | Specifies the configuration of a message queue, including its name and the messaging model with which the message queue can be used, either Point-to-Point or Publish/Subscribe. |
| Scripting | Lets you perform custom manipulations and logic to accomplish unique and advanced requirements of Integration. |
| Trading Partner | Contains the configuration details for your company or for a trading partner. |
| Communication Channel | Lets you configure a file transfer protocol, such as AS2, Disk, FTP, HTTP, OFTP2, or SFTP, to send data to and receive data from trading partners. |
| Processing Group | Increases efficiency when working with multiple trading partners by building Processing Groups. You can add, change, or remove trading partners in one location. |
| XSLT Stylesheet | Lets you apply XSLT transformations to XML or JSON documents using the Data Process step in processes. |
Editing a component
When you edit the configuration of a component, your changes take effect only when you save the component.
The following controls are available when a component is open for editing:
| Controls | Description |
|---|---|
| Save | Saves the component. The component remains open for editing. |
| Save and Close | Saves the component and closes it. |
| Close | Initiates a request to close a component without editing it. (Clicking the close icon in the component tab has the same effect). If there are no unsaved changes, the component closes immediately. If there are unsaved changes, a confirmation dialog appears. In the confirmation dialog:
|
| Previous Save | Shows the date and time of the most recently saved revision of the component. |
| Revert | Initiates a request to discard unsaved changes to the component, thereby reverting it to its configuration as of the last saved revision. In the confirmation dialog:
|
Revision History  | Opens the Revision History dialog, which provides access to the revision history of components and other information. |
